Does anyone know a way of forcing the default view in a module to always be the Standard View and preventing users from setting a different view to the default, (preferably other than modifying the menus to remove the option to set as default). Standard view does not show up in Manage views so there is no access settings that I can see. The other idea I had is a trigger to change to standard view any time a module is opened. |
Re: Maintain Standard View as the Default You could write a dxl that the admin run occasionally that reads each module and remove default settings for the module. The default view for user probably doesn't matter. |
Re: Maintain Standard View as the Default But since the processing time for resetting the default view is trivial I would indeed be tempted to make this a pre-close-module trigger deployed in the project. It may get a little sticky checking for visibility of the module and perhaps access rights but that's manageable. I think by policy you would WANT many modules to open to a specific view and defined by the project admins; you just don't want other's changing it. Perhaps create "Standard Project View" in all modules and have the trigger set the default to that (if it exists), otherwise just erase the module default. Yes, advertise to folks they make their own custom user views.
You should also write DXL to open modules to use the "Standard View" option since DXL rarely cares about the view. The following parameters are routine: read (NameMod, false, true) edit (NameMod, false, true, true) share(NameMod, false, true, true) 1st param is the full name 2nd param is whether the module is displayed (true) or invisible (false), 3rd param for 'edit' and 'share' is 'silent mode'; true means if you cannot open the module because its locked, don't bother prompting just don't open it. 'true' means the user is prompted which stops the DXL. last parameter is whether the Standard view is loaded. |
Re: Maintain Standard View as the Default I was thinking if I go the trigger route it would be to change to standard view after opening the module since the user likely would not have access to change which view is the default. However, I am going to have to take a look at a couple different ideas and see what works best for our needs. -Steve |
Re: Maintain Standard View as the Default StephenValliere - Wed Sep 07 15:27:16 EDT 2011 The pre-close-module trigger works. Folks who lack the ability to change the default view did not change it during the open session, so it won't matter if the trigger cannot change it back. Folks who CAN change the default view and do will find it changed back when they close. A pre-module-open trigger may have some luck deciding which view to load. Perhaps it could open the module read InVis and yes Standard view, and then allow the original open to proceed. Maybe someone with more view experience can chime in here.
I suppose some clever folks will change the default view then use task manager to kill DOORS, preventing the close trigger. There are some less-than-benign admins here who would propose not just changing the default view back to the standard, but flat out deleting the view altogether. Folks will take that hint. |